-
Notifications
You must be signed in to change notification settings - Fork 915
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrades jest
to v27
#1301
Upgrades jest
to v27
#1301
Conversation
45ec3a3
to
4375353
Compare
Note: the |
4375353
to
8da108a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we, if you have already, check on 1.x
the runInBand doesn't cause any issue? I believe it did but perhaps it's worth 1 more pass. If so would it be worth to have 1 commit or PR updating the github workflow another to upgrading jest. Since this can't be backported.
Yeah I can split this up into two PRs! And yes I can check |
e6fb6af
to
e670833
Compare
jest
to v27, simplifies GitHub workflowjest
to v27
ec39ceb
to
2ca8c3c
Compare
2ca8c3c
to
2645102
Compare
@@ -180,24 +187,25 @@ describe('OpenSearchDashboardsRequest', () => { | |||
|
|||
describe('events', () => { | |||
describe('aborted$', () => { | |||
it('emits once and completes when request aborted', async (done) => { | |||
// Flaky test | |||
it.skip('emits once and completes when request aborted', async () => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
are these flaky only in the CI? I was able to get the passing locally.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When you pulled the PR down it consistently passed locally for you? Sometimes it would pass, sometimes it would fail for me.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you please elaborate on the failure?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The test would timeout after 30 seconds.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see, I believe we have to make an update still: https://github.com/opensearch-project/OpenSearch-Dashboards/pull/1301/files#r818949420
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I still couldn't get this one to pass. This test doesn't use fake timers.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This might be related to the supertest
functions used, but I haven't narrowed it down.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This might be related to the
supertest
functions used, but I haven't narrowed it down.
If you aren't able to for this PR could we create a follow up issue to look into it? I don't want to block this PR any longer because it prevents an improvement that brings in more value than this test can provide but I don't want to forget about this test.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added a comment for this specifically in the issue we already have open for these types of cases: #5
* Upgrades `jest` from v26.4.2 to v27.5.1. * [CHANGELOG](https://github.com/facebook/jest/blob/v27.5.1/CHANGELOG.md) * v27 introduces breaking changes that have to be addressed. * Upgrades testing-related dependencies, removes unused dependency `babel-plugin-istanbul`, and replaces `jest-environment-jsdom-thirteen` with the built-in `jest-environment-jsdom`. This is a prerequisite to resolving opensearch-project#1231 Signed-off-by: Tommy Markley <[email protected]>
2645102
to
eeb5144
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome thanks! LGTM. Just the comment about creating a follow up issue. And probably something will need to be included as a heads up here: #1206?
Description
jest
from v26.4.2 to v27.5.1.babel-plugin-istanbul
, and replacesjest-environment-jsdom-thirteen
with the built-injest-environment-jsdom
.Issues Resolved
Prerequisite for addressing #1231
Check List
yarn test:jest
yarn test:jest_integration
yarn test:ftr